home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19971216-19980424
/
000040_news@newsmaster….columbia.edu _Fri Jan 2 21:08:37 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id VAA00300
for <kermit.misc@watsun.cc.columbia.edu>; Fri, 2 Jan 1998 21:08:36 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id VAA19408
for kermit.misc@watsun; Fri, 2 Jan 1998 21:08:36 -0500 (EST)
Path: news.columbia.edu!watsun.cc.columbia.edu!jaltman
From: jaltman@watsun.cc.columbia.edu (Jeffrey Altman)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: K/2 Gotchas
Date: 3 Jan 1998 02:08:35 GMT
Organization: Columbia University
Lines: 38
Message-ID: <68k6j3$522$1@apakabar.cc.columbia.edu>
References: <TCPSMTP.18.1.2.-16.50.0.2375661496.4897539@kincyb.com> <68k5ha$4kf$1@apakabar.cc.columbia.edu>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:8206
In article <68k5ha$4kf$1@apakabar.cc.columbia.edu>,
Frank da Cruz <fdc@watsun.cc.columbia.edu> wrote:
: : 5) Another problem was brought on when a dialup
: : script ran. Everything went OK until I went to connect mode.
: : Then, as soon as anything was entered from the keyboard, K/2
: : left connect mode back to command mode, the session froze up,
: : the cursor went to lower left-hand corner and the session seemed to become
: : unkillable. Any effort to stop the session would produce a message at the
: : bottom of the screen, something to the effect of
: : "!!! Recieved Kill Signal!!!", but the session lived on, hogging the
: : COM port, still locked up until reboot.
: :
: If you can reproduce this ("!!! Recieved Kill Signal!!!" is not one of our
: messages), you should contact kermit-support@columbia.edu and we'll see if
: we can figure out what's what. Obviously Kermit should not hang, and you
: should not need to reboot your PC to get the COM port back.
Actually, "!!! Recieved Kill Signal!!!" is one of K2's messages. It
is produced when Kermit receives a KILL signal from the operating
system. Kermit as this point stops all operations, closes the current
connection and attempts to exit.
OS/2 is designed to be robust in that a failure in an application, a
device driver, or the OS will result in the least impact on the
system. If a failure occurs in a system or device driver routine Os/2
will not allow the process to terminate until that routine completes.
This is to prevent the OS from becoming unstable. The unfortunate
side effect of this is that a device may become unusable until the OS
is restarted.
If you can reproduce this scenario with the LOG DEBUG command active
we can attempt to trace system routine in which the problem is occuring.
Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
The Kermit Project * Columbia University
612 West 115th St #716 * New York, NY * 10025 * (212) 854-1344
http://www.columbia.edu/kermit/k95.html * kermit-support@columbia.edu